I think it's a great idea, but I don't like that all the useful information other than the version goes away. Maybe, the screen could stay there, but just have text in the middle of the screen over everything that says "Screen paused"? So the info on the screen stays.
Or, since it's e-ink, when screen timeout happens, continue running the screen at half the regular update rate? Or maybe only when there is a position packet/direct message/something else?

I don't like that all the useful information other than the version goes away.

Is there any information in particular that you feel would be useful to remain on screen?

Or maybe only [update] when there is a position packet/direct message/something else?

I think what you're talking about might already be implemented with #3316
It's currently enabled for Heltec Wireless Paper and T-Echo, but hasn't been configured yet for any of the other E-Ink devices. It should be pretty straight-forward if you'd like to have a go.

At this point I'm thinking that the most diplomatic solution might be to make the screensaver behavior customizable by end-users via the app / cli. I've got this working tonight as a bit of proof of concept, but I'll have to talk to someone more knowledgable about whether it's an appropriate option, and about would it would take to expose the setting in the mobile apps.

I think it would be useful to have the node id remain visible on the screensaver. If you have multiple devices sleeping, you can determine at glance which is which.

I think it would be useful to have the node id remain visible on the screensaver. If you have multiple devices sleeping, you can determine at glance which is which.

Good call! I'll look at getting that onto the icon screen, maybe replacing the version number?

The new plan is: offer users a choice in the display preferences.

• LOGO
  Similar to screen shown in original post

• OVERLAY
  Some sort of minimal "heads up", drawn over the existing (pre-pause) screen image. Proof-of-concept working, but haven't thought about a design yet.

• BLANK
  Just wipe the display

• NONE
  No action taken (current behavior)

• CUSTOM
  A custom GFX method, only built if method is set in variant's platformio.ini build_flags.
  Supports vendors and DIYers to make their own aesthetic choices.

  #define EINK_CUSTOM_SCREENSAVER helloWorld
  
  #ifdef EINK_CUSTOM_SCREENSAVER
  namespace einkCustomScreensavers
  {
    void helloWorld(OLEDDisplay *display)
    {
      display->setTextAlignment(TEXT_ALIGN_LEFT);
      display->drawString(30, 30, "Hello world!");
    }
  }
  #endif

Not sure if it'll go ahead or not; just waiting for input from the dev-team about it.

@jimwhitelaw

I think it would be useful to have the node id remain visible on the screensaver.

Node ID, "last 4 of Node ID" or short-name?

I'm thinking maybe short-name and "last 4 of NodeID"?

I think any id that fits nicely on the display. Last 4 is fine, short name is possibly friendlier. As long as sleeping units can be identified, you’re golden.

Following feedback on meshtastic/protobufs#474, scope of this pull-request is reduced. A single screensaver behavior will be implemented. Abandoned work-in-progress is mothballed as eink-screensaver-configurable branch.

After some time spent yesterday developing the different screensaver options, my personal opinion now is that the subtle overlay suggestion is best #3477 (comment). This also meets the criteria that nodes should be identifiable with the screen off #3477 (comment).

Tested Heltec Wireless Paper V1.0 and V1.1
No issues expected, but be aware that no testing has taken place with different resolutions / platforms.

I like the simple overlay, although depending on which screen it was showing, it may or may not show the ID of the node itself.

Formatting on the T-Echo looks good as well:

When you're testing, are you rebooting and then shutting down within roughly the first 30 seconds?

No, it was more than that. I set the screen timeout on 60 seconds, so I waited at least that. I just tested with several minutes in between and it still happens.

Do you have any suggestions here from a design point of view about where and how to display this info? Do you prefer "last 4" of node id, or short name?

To be honest for me displaying it on the screen is not so important, you can also mark the device itself with a sticker. I'm fine with the current approach.

No, it was more than that. I set the screen timeout on 60 seconds, so I waited at least that. I just tested with several minutes in between and it still happens.

Thanks for that info. I think I might have a fix, but not sure just yet. I should actually have a T-Echo turning up in the next day or two, so I can check then whether I've solved it or not.

To be honest for me displaying it on the screen is not so important, you can also mark the device itself with a sticker. I'm fine with the current approach.

I've modified the design slightly now to include short name, and I'm fairly pleased with how it looks. I'll push that in the near-future too.

There's a slight hold up on those final tweaks: I found a low-down bug in the system. When the screen class turns off, there are no more calls to display(), which is where the async-refresh code polls for completion. This means that when the screensaver is displayed, the panel's voltage generating hardware remains active.

A quick fix for this would be to use a blocking fast-refresh here, but I'd rather try tackle the problem at its source. I'm looking into inheriting the OSThread class, to allow polling after the screen is "turned off".

There is a variation of osthteads called the notified worker. It will not loop but execute a task when externally notified. Maybe this one is better suited.

Short name is displayed on overlay.

And for the third time tonight, I'm going to claim that everything is final now. Except that this time I'm going to bed so I have to leave it alone..

Reference doc, for future maintenance:

Async Refresh (updated)	Refresh Selection (updated)	Screensaver